PR for next LTS release (0.68.7) - #2330
Conversation
5d46f05 to
f10ee67
Compare
Signed-off-by: immanuwell <pchpr.00@list.ru>
There was a problem hiding this comment.
1 issue found across 6 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="docs/CHANGELOG.md">
<violation number="1" location="docs/CHANGELOG.md:16">
P2: Custom agent: **Changelog Review Agent**
Changelog entry describes internal implementation detail (adding a struct field) instead of a user-visible fix. The rule requires user-centric explanations and prohibits describing internal implementation details.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Fix all with cubic | Re-trigger cubic
|
|
||
| ## tip | ||
|
|
||
| * BUGFIX: [vmanomaly](https://docs.victoriametrics.com/operator/resources/vmanomaly/): add missing `scatter_infer_jobs` field to the periodic scheduler config struct. See [#2328](https://github.com/VictoriaMetrics/operator/issues/2328). |
There was a problem hiding this comment.
P2: Custom agent: Changelog Review Agent
Changelog entry describes internal implementation detail (adding a struct field) instead of a user-visible fix. The rule requires user-centric explanations and prohibits describing internal implementation details.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/CHANGELOG.md, line 16:
<comment>Changelog entry describes internal implementation detail (adding a struct field) instead of a user-visible fix. The rule requires user-centric explanations and prohibits describing internal implementation details.</comment>
<file context>
@@ -13,6 +13,8 @@ aliases:
## tip
+* BUGFIX: [vmanomaly](https://docs.victoriametrics.com/operator/resources/vmanomaly/): add missing `scatter_infer_jobs` field to the periodic scheduler config struct. See [#2328](https://github.com/VictoriaMetrics/operator/issues/2328).
+
## [v0.68.6](https://github.com/VictoriaMetrics/operator/releases/tag/v0.68.6)
</file context>
| * BUGFIX: [vmanomaly](https://docs.victoriametrics.com/operator/resources/vmanomaly/): add missing `scatter_infer_jobs` field to the periodic scheduler config struct. See [#2328](https://github.com/VictoriaMetrics/operator/issues/2328). | |
| * BUGFIX: [vmanomaly](https://docs.victoriametrics.com/operator/resources/vmanomaly/): allow configuring `scatter_infer_jobs` in the periodic scheduler. Previously this option was missing and its value was silently ignored. See [#2328](https://github.com/VictoriaMetrics/operator/issues/2328). |
ff2a385 to
d09a187
Compare
….12.2 (#2149) * chore(deps): update module github.com/golangci/golangci-lint/v2 to v2.12.2 * chore: use reflect.Pointer to fix `inline: Constant reflect.Ptr should be inlined` --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Vadim Rutkovsky <vadim@vrutkovs.eu>
a53bc08 to
a78e807
Compare
There was a problem hiding this comment.
3 issues found across 31 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="internal/controller/operator/factory/vmsingle/rbac.go">
<violation number="1" location="internal/controller/operator/factory/vmsingle/rbac.go:76">
P1: VMSingle reconciliation never invokes this function, so no Role, RoleBinding, ClusterRole, or ClusterRoleBinding is created for a managed ServiceAccount. Wire it into `CreateOrUpdate` after ServiceAccount reconciliation, passing `config.MustGetBaseConfig().WatchNamespaces`; current tests only exercise the helper directly.</violation>
</file>
<file name="api/operator/v1beta1/vmprobe_types.go">
<violation number="1" location="api/operator/v1beta1/vmprobe_types.go:57">
P2: Replacing `+deprecated` with `+notes` drops the machine-readable OpenAPI deprecation annotation for these two fields. `+deprecated` is a standard k8s `openapi-gen` marker that generates `deprecated: true` in the OpenAPI spec; `+notes` is not recognized by any standard tool. Consumers such as API clients, IDEs, and generated docs will no longer see `StaticConfig` and `Ingress` as deprecated. If the project intended a custom annotation format, add a processor for `+notes` or keep both markers.</violation>
</file>
<file name="docs/CHANGELOG.md">
<violation number="1" location="docs/CHANGELOG.md:18">
P3: VMAnomaly version in changelog tip section says v1.28.6 but the code at HEAD has v1.29.7 (up from v1.29.6 on release-0.68). Update version to v1.29.7 and fix the link anchor to #v1297.</violation>
</file>
Tip: instead of fixing issues one by one fix them all with cubic
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
|
|
||
| // createK8sAPIAccess creates RBAC access rules for vmsingle. | ||
| // namespaces is the list of watched namespaces; an empty slice means cluster-wide access. | ||
| func createK8sAPIAccess(ctx context.Context, rclient client.Client, cr, prevCR *vmv1beta1.VMSingle, namespaces []string) error { |
There was a problem hiding this comment.
P1: VMSingle reconciliation never invokes this function, so no Role, RoleBinding, ClusterRole, or ClusterRoleBinding is created for a managed ServiceAccount. Wire it into CreateOrUpdate after ServiceAccount reconciliation, passing config.MustGetBaseConfig().WatchNamespaces; current tests only exercise the helper directly.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At internal/controller/operator/factory/vmsingle/rbac.go, line 76:
<comment>VMSingle reconciliation never invokes this function, so no Role, RoleBinding, ClusterRole, or ClusterRoleBinding is created for a managed ServiceAccount. Wire it into `CreateOrUpdate` after ServiceAccount reconciliation, passing `config.MustGetBaseConfig().WatchNamespaces`; current tests only exercise the helper directly.</comment>
<file context>
@@ -0,0 +1,228 @@
+
+// createK8sAPIAccess creates RBAC access rules for vmsingle.
+// namespaces is the list of watched namespaces; an empty slice means cluster-wide access.
+func createK8sAPIAccess(ctx context.Context, rclient client.Client, cr, prevCR *vmv1beta1.VMSingle, namespaces []string) error {
+ if len(namespaces) == 0 {
+ if err := ensureCRExist(ctx, rclient, cr, prevCR); err != nil {
</file context>
| type VMProbeTargets struct { | ||
| // StaticConfig defines static targets which are considers for probing. | ||
| // +deprecated={deprecated_in: "v0.68.0", removed_in: "v0.71.0", replacements: {static}} | ||
| // +notes={deprecated_in: "v0.68.0", removed_in: "v0.71.0", replacements: {static}} |
There was a problem hiding this comment.
P2: Replacing +deprecated with +notes drops the machine-readable OpenAPI deprecation annotation for these two fields. +deprecated is a standard k8s openapi-gen marker that generates deprecated: true in the OpenAPI spec; +notes is not recognized by any standard tool. Consumers such as API clients, IDEs, and generated docs will no longer see StaticConfig and Ingress as deprecated. If the project intended a custom annotation format, add a processor for +notes or keep both markers.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At api/operator/v1beta1/vmprobe_types.go, line 57:
<comment>Replacing `+deprecated` with `+notes` drops the machine-readable OpenAPI deprecation annotation for these two fields. `+deprecated` is a standard k8s `openapi-gen` marker that generates `deprecated: true` in the OpenAPI spec; `+notes` is not recognized by any standard tool. Consumers such as API clients, IDEs, and generated docs will no longer see `StaticConfig` and `Ingress` as deprecated. If the project intended a custom annotation format, add a processor for `+notes` or keep both markers.</comment>
<file context>
@@ -54,7 +54,7 @@ type VMProbeSpec struct {
type VMProbeTargets struct {
// StaticConfig defines static targets which are considers for probing.
- // +deprecated={deprecated_in: "v0.68.0", removed_in: "v0.71.0", replacements: {static}}
+ // +notes={deprecated_in: "v0.68.0", removed_in: "v0.71.0", replacements: {static}}
// +optional
StaticConfig *VMProbeTargetStatic `json:"staticConfig,omitempty"`
</file context>
|
|
||
| * Dependency: [vmoperator](https://docs.victoriametrics.com/operator/): Updated default versions for VM apps to [v1.147.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.147.0) version | ||
| * Dependency: [vmoperator](https://docs.victoriametrics.com/operator/): Updated default versions for VT apps to [v0.9.4](https://github.com/VictoriaMetrics/VictoriaTraces/releases/tag/v0.9.4) version. | ||
| * Dependency: [vmoperator](https://docs.victoriametrics.com/operator/): Updated default versions for VMAnomaly to [v1.28.6](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1286) version |
There was a problem hiding this comment.
P3: VMAnomaly version in changelog tip section says v1.28.6 but the code at HEAD has v1.29.7 (up from v1.29.6 on release-0.68). Update version to v1.29.7 and fix the link anchor to #v1297.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At docs/CHANGELOG.md, line 18:
<comment>VMAnomaly version in changelog tip section says v1.28.6 but the code at HEAD has v1.29.7 (up from v1.29.6 on release-0.68). Update version to v1.29.7 and fix the link anchor to #v1297.</comment>
<file context>
@@ -13,7 +13,16 @@ aliases:
+* Dependency: [vmoperator](https://docs.victoriametrics.com/operator/): Updated default versions for VM apps to [v1.147.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.147.0) version
+* Dependency: [vmoperator](https://docs.victoriametrics.com/operator/): Updated default versions for VT apps to [v0.9.4](https://github.com/VictoriaMetrics/VictoriaTraces/releases/tag/v0.9.4) version.
+* Dependency: [vmoperator](https://docs.victoriametrics.com/operator/): Updated default versions for VMAnomaly to [v1.28.6](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1286) version
+
+* SECURITY: [vmagent](https://docs.victoriametrics.com/operator/resources/vmagent/), [vmsingle](https://docs.victoriametrics.com/operator/resources/vmsingle/): remove cluster-wide `secrets` and `configmaps` permissions from the operator-managed `ClusterRole`. Secret access for the config-reloader is now granted via a namespace-scoped `Role` limited to the single operator-managed config secret. For `vmsingle` in ingest-only mode (the default), no secret or configmap permissions are granted at all.
</file context>
| * Dependency: [vmoperator](https://docs.victoriametrics.com/operator/): Updated default versions for VMAnomaly to [v1.28.6](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1286) version | |
| * Dependency: [vmoperator](https://docs.victoriametrics.com/operator/): Updated default versions for VMAnomaly to [v1.29.7](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1297) version |
881eb0f to
c6dad2b
Compare
* internal/config: update VM_METRICS_VERSION to v1.147.0 Changelog [v1.147.0](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/docs/victoriametrics/changelog/CHANGELOG.md#v11470) Signed-off-by: Max Kotliar <mkotlyar@victoriametrics.com> * cleanup changelog --------- Signed-off-by: Max Kotliar <mkotlyar@victoriametrics.com>
c6dad2b to
d533ba7
Compare
ae15efd to
9abe297
Compare
| } | ||
| if rw.OAuth2 != nil && rw.OAuth2.ClientSecret != nil { | ||
| return true | ||
| } |
There was a problem hiding this comment.
no TLS secrets here
| @@ -0,0 +1,228 @@ | |||
| package vmsingle | |||
There was a problem hiding this comment.
vmsingle supports scraping only starting 0.69.0, so rbac is not needed
9abe297 to
102c893
Compare
102c893 to
0e60692
Compare
0e60692 to
0f7e1d6
Compare
No description provided.